We have assembled a list of the most common questions and answers about Traveler Companion for Windows Phone below. If you are having problems with Traveler Companion, please look over this information first to see if your question has already been answered.

Traveler Companion for Windows Phone is a Windows Phone 8 application that works in conjunction with an IBM Notes Traveler mail account configured for use with the on board Windows Phone 8 mail application.  Traveler Companion for Windows Phone provides users the ability to read, compose, reply to, and forward Domino encrypted mail messages. Messages sent from Traveler Companion can be sent either encrypted or unencrypted. Encrypted messages are encrypted using Notes standard encryption.

Before you start using your Companion application, the following requirements must be met:

• Your Domino administrator must update your IBM Notes Traveler server to version 9.0.1 IF1 (build version 9.0.1.0 201311221344) or higher
• You must already have IBM Notes Traveler mail support configured and working on your Windows Phone 8 device
• You must have a copy of your Notes ID file stored in your mail file or placed in the ID Vault by your Domino administrator

Traveler Companion is available from the Windows Phone Store. The simplest way to install it is to use the Store app on your Windows Phone 8 device, and search for Companion, and then install Traveler Companion from its app entry.

Once you select View this message within an encrypted message in the mail application, you will be taken to the Companion application, which will automatically be pre-filled with default configuration settings, as well as the User name and Server Address. However, if you directly open the Companion application for the first time, the Settings panel will appear. From here, you can perform a manual configuration by providing the following information:

• User name that you use to connect to the IBM Notes Traveler server
• Password for your user name
• Host address of your IBM Notes Traveler server. For example, myserver.mycompany.com. If your installation of IBM Notes Traveler requires a custom connection port, include the port number as part of the address.  For example, myserver.mycompany.com:15000.  Do not include https:// or any other prefix to the host address.

You will need your IBM Notes Traveler administrator's help to fix this, and there are two possible causes.

First, your IBM Notes Traveler server may be on an older code level. Traveler Companion requires at least version 9.0.1 IF1 of the IBM Notes Traveler server. If your IBM Notes Traveler server is at the latest code level, your administrator may have disabled your encrypted mail access by setting the server notes.ini parameter, NTS_ENCRYPTION_ENABLED, to false. The server will have to be restarted after setting it to true and then the mail resynced to get the link.

For mail decryption to operate, a user's IBM Notes ID file must be either uploaded to their mail file or placed in a credential vault by your Domino administrator. If you are able to send and receive encrypted mail from IBM iNotes, you should already have a Notes ID file available for IBM Notes Traveler. To check your Notes ID status, and if necessary, upload your Notes ID file to the mail file, perform the following procedure:

1. From a computer where you have IBM Notes or have a copy of your Notes ID file, open a web browser to https://[yourserver]/traveler.
   NOTE: If your server is not using SSL, open a web browser to http://[yourserver]/traveler.
2. Select Manage the Notes ID. If you already have a Notes ID available, the page that appears will tell you. In this case, it is not necessary to proceed any further.
3. Select Upload Notes ID.
4. In the Notes ID File field, enter the location of your Notes ID file.
5. In the Password field, enter your Notes ID password.
6. Select Upload Notes ID.

Depending on the security policies that your organization has in place, you may be required to change your passwords periodically. If your IBM Notes Traveler password changes, you will need to change your IBM Notes Traveler password in the Traveler Companion Settings panel.

If you need to change the password on your IBM Notes ID file, you can do so through IBM Notes Traveler or IBM iNotes. If you are using a vaulted Notes ID, you may also change your password through the IBM Notes client. These instructions are for using IBM Notes Traveler to change your Notes ID password. Please see the IBM Notes and Domino wiki for information on using the other procedures.

NOTE: You only need to change the password once, so if you have changed your Notes ID password using IBM iNotes or IBM Notes, you do not need to perform the following procedure.

To use IBM Notes Traveler to change your password, perform the following procedure:

1. Open a web browser to https://[yourserver]/traveler. You can do this from another computer or from your Windows Phone device.
2. Select Manage the Notes ID.
3. Select Change the Notes ID Password and follow the instructions.
4. Once your password has been changed, you must supply the new password the next time Traveler Companion prompts you.

If you are having problems with the application, you are encouraged to contact IBM support to open a PMR. Through the support process, we will determine if the problem exists in the Traveler Companion app or the Notes Traveler server. Server-related problems will be addressed, and fixes made available through the IBM Passport Advantage support process. If your PMR requires a fix to Traveler Companion, the fix will be considered for an updated version of Traveler Companion to be made available through the Windows Phone Store. Please note that the delivery schedule and process for obtaining Traveler Companion updates and fixes differs from IBM Passport Advantage support, due to the Windows Phone Store being the distribution channel.

To enable logging, please tap the Additional settings button on the Settings panel in Traveler Companion. Logging is OFF by default. Touch the slider to change it to ON. Once Logging is enabled, you can also control the level of logging and the maximum log size.

If you think you have found a problem with Traveler Companion, please follow the process described below and open a support ticket with IBM (a problem management record or PMR):

In Companion, first ensure Logging is turned on and the logging level is set to All. Next, reproduce the problem.

If you are using Companion 1.0, do the following:

1. From the Settings panel in Companion, tap ... at the bottom and then choose view log.
2. The icon on the lower left will allow you to forward the log contents as a mail message. Send this to your System Administrator with as much detail as possible, as well as the steps to reproduce the problem. Also include screenshots, if possible.

​If you are using Companion 1.1 do the following:

1. From the Settings panel in Companion, tap ... at the bottom and then choose create problem report option.
2. Select the type of problem from the choices provided in the drop down.
3. Provide a description of the problem and the steps to reproduce.
4. Attach any screenshots that can help in problem determination.
5. Select the check mark icon at the bottom to send this to your System Administrator.
   
   For problems with the rendering of mail, screenshots are often helpful. In Windows Phone 8 you are able to save a screenshot by holding both the power button (often on the side of the phone) and the Windows button (middle button under the screen). Screenshots are saved in the Screenshot album of the Picture Hub 

To enable "do not copy", from within the email you are currently composing, please tap ... at the bottom and select privacy option. 

On the Settings panel in Traveler Companion tap ... and select the Help menu item. Scroll to the bottom of the About page to find the Version and Build numbers.

Updates will be distributed through the Windows Phone Store. 

Traveler Companion 1.1.0 has the following new additions:

Companion can not handle untrusted or self signed certificates at this time. Please change to use certificates from Trusted Authority.

Currently there has been no work done with testing Companion with any MDM providers. If Companion works as expected without MDM and does not work with MDM, please work with your MDM provider to address the issues.